Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/docs-npm/api/models.mdx`:
- Around line 104-110: The docs reference the non-existent TypeScript file
src/core/models.ts; update the link and text to point to the actual Python
source refactron/core/models.py (or explicitly state this doc targets a separate
JS/TS package if that was intended) and ensure the types mentioned
(PipelineSession, FixQueueItem, FixStatus) are referenced to their Python
definitions or a note is added clarifying language mismatch.

In `@docs/docs-npm/cli/analyze.mdx`:
- Around line 40-42: The "Supported language detected" link currently points
only to /docs-npm/languages/python which is too narrow; update the link target
in the docs text "Supported language detected for the project. See
[Languages](/docs-npm/languages/python)." to point to a neutral languages index
(e.g., /docs-npm/languages) or include links to both relevant pages (e.g.,
Python and TypeScript) so Node users aren't misrouted; edit the link target text
in docs/docs-npm/cli/analyze.mdx accordingly.

In `@docs/docs-npm/cli/issue-browser.mdx`:
- Around line 28-39: The docs table for the issue browser is missing the
severity drill-in and navigation keybindings used by the interactive viewer;
update the CLI docs page (issue-browser.mdx) to include the keys `1`-`4` for
drilling into severity groups and `n`/`p`/`b`/`q` for next/previous/back/quit
navigation, and add a short note that `refactron analyze` launches the TTY
interactive issue viewer with severity-grouped navigation and falls back to
non-interactive output for CI/CD; reference the interactive issue
viewer/keybinding descriptions in the same table and adjacent paragraph so
readers see the mapping next to existing entries like `↑`/`↓`, `d`, `a`, `A`,
`v`, `/`, `g`/`G`, and `q`.

In `@docs/docs-npm/concepts/verification.mdx`:
- Around line 8-9: The doc incorrectly states checks are selected by blast
radius; update the "Verification Engine" documentation to state that
VerificationEngine always initializes and runs all three checks (syntax, medium,
test gate) sequentially, short-circuiting on the first failure, rather than
skipping checks by blast level; specifically replace any wording that says
checks are chosen by blast radius or that the test gate runs only for
high/critical with a clear description of the current implementation
(VerificationEngine initializes all checks and executes them in order), and
optionally add a note that blast-level-based skipping is a planned/possible
enhancement if desired.

In `@docs/docs-npm/configuration.mdx`:
- Around line 8-49: The docs show nested config sections (analyzers.*,
verification.*, autofix.*, output.*) but the loader expects flat fields passed
into RefactronConfig via RefactronConfig.from_file (refactron/core/config.py),
causing TypeError/ConfigError; fix by updating this example YAML to the flat
top-level shape that RefactronConfig expects (use the exact field names from the
RefactronConfig dataclass) or alternatively modify RefactronConfig.from_file to
deep-merge and normalize nested sections into the flat dict before calling
cls(**config_dict); reference RefactronConfig and from_file to locate the code
to change.

In `@docs/docs-npm/quickstart.mdx`:
- Line 9: Update the prerequisite sentence in quickstart.mdx to stop claiming
Git enables "blast radius": edit the line that currently reads "**Git**
(optional but recommended — enables temporal analysis and blast radius)" to
remove "and blast radius" so it only states that Git enables temporal analysis;
keep the rest of the phrasing intact to avoid conflicting guidance about
structural (blast radius) analysis being separate.

---

Nitpick comments:
In `@docs/docs-npm/api/overview.mdx`:
- Around line 8-11: Update the docs text to recommend importing from the
package's published entry points (the package.json "exports") instead of deep
`dist/...` paths: replace or reword the sentence that references
`dist/cli/index.js` and examples like `dist/core/models.js` /
`dist/core/orchestrator.js` to stress using the exported entrypoints (e.g.,
top-level package imports or named exports defined in package.json) as the
supported public API for the `refactron` CLI and library; keep a short note that
deep `dist/*` imports may break across releases and point readers to check
package.json "exports" for valid import paths.

In `@docs/docs-npm/cli/verify.mdx`:
- Around line 8-14: Update the CLI usage synopsis so it explicitly shows
session-wide mode in the code block that currently reads "verify [file]"; change
it to include "." and the no-arg form (for example "verify [file|.]" or a
two-line snippet like "verify [file]" and "verify" / "verify .") so the usage
aligns with the explanatory text about "." and no-arg behavior in the same
section.

In `@docs/docs-npm/quickstart.mdx`:
- Line 30: Replace the hardcoded header "# 0.1.0-beta.2" in the quickstart
output example with a placeholder-style value so the docs don't go stale; e.g.,
change the string "0.1.0-beta.2" (found in the header line "# 0.1.0-beta.2") to
a generic placeholder such as "<cli-version>" or "{{cli_version}}" and update
any adjacent explanatory text to refer to the placeholder.